Every MES RFP eventually collapses into the same uncomfortable question: how much of what you already have are you going to have to throw away? For discrete manufacturers sitting on a Wonderware-era historian, a homegrown SCADA layer, or an Ignition deployment that’s grown organically for a decade, that question matters more than any feature matrix. This year it’s sharper than usual, because both major players in this comparison have changed the ground under the decision. Siemens has moved Opcenter Execution to a subscription-only commercial model, and AVEVA has been pushing harder on a unified, AI-ready bundling of its MES and historian products. Neither shift is cosmetic. Both change what a replatform actually costs you in migration effort, not just in license fees.
This isn’t a spec-sheet comparison — both platforms handle work orders, genealogy, quality holds, and OEE tracking competently, and any vendor demo will look clean. The real differentiator, especially for shops migrating off legacy historian/SCADA stacks, is friction: how much of your tag structure, your equipment model, and your operator workflows survive the cutover versus needing to be rebuilt from scratch.
What each platform actually is
AVEVA MES is the modern name for what long-time users still think of as Wonderware MES, now positioned as part of AVEVA’s broader unified operations suite alongside AVEVA Historian, AVEVA System Platform, and AVEVA’s PI-adjacent data layer following the OSIsoft acquisition. AVEVA’s pitch in 2026 is architectural consolidation: one data model, one historian backbone, one licensing conversation, spanning SCADA, historian, and MES. For a shop already running Wonderware InTouch, System Platform, or Wonderware Historian, that’s a meaningful claim, because it implies the tag namespace and asset model you already built don’t have to be reinvented.
Siemens Opcenter Execution is part of the Opcenter portfolio built on the old Camstar and SIMATIC IT lineage, aimed squarely at discrete and hybrid discrete-process manufacturers with complex routings, genealogy, and regulatory traceability needs. Opcenter’s strength has traditionally been depth on the manufacturing execution model itself — configurable workflows, electronic work instructions, and integration into the Teamcenter/PLM side of the Siemens Xcelerator portfolio. The 2026 shift to subscription-only pricing brings Opcenter in line with where much of the enterprise software market has gone, but it does reset the TCO conversation for shops that had budgeted around perpetual-license assumptions.
The migration question nobody puts in the RFP
Ask a vendor “does your MES integrate with our historian” and you’ll always get yes. Ask “how much of my existing tag hierarchy and asset naming survives, unmodified, in your data model” and you get a much more honest conversation.
Coming off Wonderware / System Platform
If your existing environment is Wonderware-flavored — System Platform Galaxy, ArchestrA objects, Wonderware Historian tag structures — AVEVA MES has a structural advantage simply by lineage. The ArchestrA object model and the underlying tag namespace map more directly into AVEVA’s current MES and historian tooling because they share ancestry. That doesn’t mean zero rework; ArchestrA templates built a decade ago under different naming conventions will still need review, and any AVEVA cloud-adjacent components will ask you to rationalize tag naming for their unified namespace. But you’re extending a family tree, not grafting onto a different one. In our assessment, this is the single strongest practical argument for AVEVA MES in a 2026 replatform: it’s the path of least resistance for the specific population of plants still running legacy Wonderware infrastructure.
Coming off Ignition or a homegrown stack
This is where the comparison gets more even, and arguably more interesting. Shops running Ignition (from Inductive Automation) or a bespoke SCADA/historian combination don’t have “home-field advantage” with either vendor — both AVEVA MES and Opcenter Execution will require you to build an integration layer, typically via OPC UA or MQTT Sparkplug B, to bridge your existing tag structure into their respective data models. Neither platform natively speaks Ignition’s tag provider structure out of the box.
The difference shows up in how each platform wants you to model the plant. Opcenter Execution leans on a more rigid, ISA-95-aligned execution model — work centers, operations, routings — which can actually simplify migration if your Ignition tag structure was already loosely organized around equipment hierarchy, because you’re mapping into a well-defined schema rather than negotiating a looser one. AVEVA MES, particularly when paired with System Platform, gives you more flexibility in object modeling but that flexibility means more up-front design decisions rather than a prescribed template. Neither is objectively “less work” — it depends on how disciplined your existing tag naming already is. Shops with clean, ISA-95-influenced tag hierarchies in Ignition will find Opcenter’s structure easier to map into. Shops with sprawling, ad hoc historian tags may find AVEVA’s flexibility easier to bend around what already exists rather than forcing a rebuild.
Licensing and subscription shift: read the fine print, not the pitch
Siemens’ 2026 move to subscription-only Opcenter licensing is the more consequential commercial change here. For manufacturers used to perpetual licensing with maintenance fees, this is a real shift in cash flow and total cost of ownership modeling, not just a pricing tweak — it changes how finance teams need to model the investment over a multi-year horizon, and it’s worth walking through with your Siemens account team explicitly before RFP scoring, rather than assuming legacy TCO spreadsheets still apply.
AVEVA has been moving toward consumption- and subscription-based models as well, particularly as it bundles MES with its historian and analytics layers under a unified commercial construct. The practical implication for both vendors: don’t score this RFP on license cost alone using last cycle’s assumptions. Get explicit subscription terms, renewal escalators, and what happens to your data and tag configuration if you ever decide to walk away — portability of your engineering work product should be a contract line item, not an afterthought.
Who fits where
AVEVA MES is the stronger fit if you’re currently on Wonderware/System Platform and want to preserve as much of your existing engineering investment as possible while modernizing toward a unified historian-and-MES data backbone. It also suits shops that want flexibility in how they model equipment and processes rather than conforming to a fixed execution schema.
Opcenter Execution tends to suit discrete manufacturers with complex routings, strong PLM integration needs (especially if you’re already in the Siemens Xcelerator/Teamcenter ecosystem), and a preference for a more structured, ISA-95-driven execution model — particularly if your existing tag discipline is already reasonably clean. It may suit less well shops looking for the lightest possible integration lift from a sprawling, undisciplined historian environment, since its more rigid schema demands more upfront normalization work.
Neither platform will hand you a copy-paste migration from Ignition or a homegrown stack — budget real engineering time for tag mapping, asset model design, and validation regardless of which you choose. The honest differentiator in 2026 isn’t which platform has better dashboards. It’s which one’s underlying assumptions about your data already match the mess you’re trying to clean up.
This article was written with the assistance of artificial intelligence. While we aim for accuracy, the information may be incomplete, out of date, or incorrect, and should be independently verified before you rely on it for any decision. It is provided for general information only and does not constitute professional advice.
